C-Worthy (R) Message Librarian Data File Version 1.0
COPYRIGHT (C) 1985 - 1988. All Rights Reserved.
Custom Design Systems, Inc. Provo, Utah USA.
Insert Disk %d in Drive %c.
DESCRIPTION
The description for this error is not available.
ERROR
Try Another Disk
Further program execution is not possible.
SEVERITY
Program execution should continue normally.
The current operation cannot be completed.
successful
Trace Message
Please Wait
The system error library file "%s" is missing.
No current client/contact selected.
Invalid DDE topic.
Not enough system memory is available to do the function required. Make more memory available.
Invalid or missing DDE item.
An attempt to seek to a specific position in the file "%s" failed.
An attempt to read from the file '%s' failed during a read request for %u bytes. Possible cause: premature end of file was found.
An attempt to read from the file "%s" failed. The read request was for %u bytes.
An attempt to read from the file '%s' failed during a read request for %u bytes. Possible cause: trying to read past the end of the file.
An attempt was made to push a list on the list stack, and the list stack is already full.
An attempt was made to pop a list from the list stack, and the list stack was empty.
Invalid format.
Out of memory.
An attempt to allocate %u bytes of additional memory failed. Make more memory available.
An attempt to open the file "%s" failed.
An attempt to close the file "%s" failed.
An attempt to write to the file '%s' failed during a write request for %u bytes. Possible cause: the disk is full.
An attempt to write to file "%s" failed. The write request was for %u bytes.
An attempt was made to get the first element in a list and the list was empty.
January
February
March
April
August
September
October
November
December
Sunday
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Invalid DDE item.
Maximizer is currently busy.
Current record no longer exists.
Number of fields per column cannot exceed 20.
You cannot enter a high value without also entering a low value.
No database opened.
Parameter 1 is missing or invalid on the current operation.
Search item not supported.
Operation cannot be completed in the Maximizer's currently active MDI window.
Parameter 2 is missing or invalid on the current operation.
Parameter 3 is missing or invalid on the current operation.
Parameter 4 is missing or invalid on the current operation.
Invalid DDE execute command.
A wildcard asterisk (*) must be either in the first or the last position of the value.
An attempt was made to set Dynamic Message Number %d. There is no such dynamic message pointer.
When you are using both a low and a high value, you must either have wildcard question marks in both vales (ie exactly the same positions), or in neither value.
When you are using both a low and a high value, both values must have the same format (e.g. the wildcard question marks must be in exactly the same position(s) in both values).
Invalid note DDE poke command.
Invalid clipboard format.
Attempt to open the clipboard failed.
Attempt to poke field failed. Field length is too long
Attempt to poke item failed. Data is in an invalid format.
Attempt to poke item failed. Item is not supported.
No fields to update.
Attempt to execute update option failed. the update option is invalid.
Record has been made private to another user.
Parameter 5 is missing or invalid on the current operation
Parameter 6 is missing or invalid on the current operation.
Parameter 7 is missing or invalid on the current operation.
Parameter 8 is missing or invalid on the current operation.
Parameter 9 is missing or invalid on the current operation.
Parameter 10 is missing or invalid on the current operation.
Invalid or missing client ID.
Insufficient Client/Contact rights to complete the current operation.
The high value is lower than the low value.
Insufficent Category rights to complete the following operation.
Insufficent Note rights to complete the current operation.
GetMessage was called, but no message was specified.
GetMessage was called, but the requested system message has been deleted.
An unknown procedure
GetError was called, but the specified procedure has been deleted.
When you are using both a low and a high value, the wildcard asterisk (*) must be in the last position of the search values.
Hotlist date range cannot be greater than one year.
Set marked Hotlist entries to completed.
Set marked Hotlist entries priority to '%s'
Insufficent Category setup rights to complete the following operation.
Last Name/Company Name is a required field.
Insufficent Alternate Address rights to complete the current operation.
Parameter 11 is missing or invalid on the current operation.
Parameter 12 is missing or invalid on the current operation.
Parameter 13 is missing or invalid on the current operation.
Parameter 14 is missing or invalid on the current operation.
Parameter 15 is missing or invalid on the current operation.
Parameter 16 is missing or invalid on the current operation.
Parameter 17 is missing or invalid on the current operation.
Parameter 18 is missing or invalid on the current operation.
Parameter 19 is missing or invalid on the current operation.
Parameter 20 is missing or invalid on the current operation.
No error description is available.
Insufficent Document rights to complete the current operation.
OpenDataBase execute command failed.
OLE returned an error code of %d. %s
OLE Remote procedure call returned an error code of %d. %s
OLE Dispatch returned an error code of %d. %s
OLE Storage returned an error code of %d. %s
OLE ITF returned an error code of %d. %s
OLE 'UNKNOWN' returned an error code of %d. %s
Application needed for this object or one of its components can not be found. The current operation cannot be completed.
Insufficient memory available. The current operation cannot be completed.
Access to this operation has been denied. The curretn operation cannot be completed.
Insufficient disk space to complete the operation.
Operation aborted due to insufficient access rights.
The Server Application, source file, or item cannot be found. Make sure the application is properly installed, and that it has not been deleted, moved, or renamed.
A INSUFFICIENT SYSTEM MEMORY error has occurred on the '%s' file. Either decrease the value for the cache allocation configuration option, decrease the number of remote sessions option or add memory to the sever.
A NO CACHE BUFFERS AVAILABLE error has occurred on the %s file. Either increase the cache allocation option, or if doing a Database restore/convert re-do the operation without using the primary method
You must exit Windows and load SHARE.EXE to use OLE 2.0.
A MEMORY ALLOCATION error has occurred on the '%s' file. Ensure that the workstation has sufficient conventional memory prior to starting Windows.
An INCORRECT DESCRIPTOR error occurred on the '%s' file. The descriptor structure in the data buffer is incorrect, or inconsistant.
A DEADLOCK CONDITION error occurred on the '%s' file. The application should clear all resources before proceeding. This breaks the deadlock condition, and allows other applications to access resources for which they are waiting.
An INSUFFICIENT STACK SPACE AVAILABLE error occurred on the '%s' file. The Btrieve engine has run out of stack space.
A CHUNK OFFSET TOO LARGE error has occurred on the '%s' file. A chunk operation has specified an offset beyond the end of the record.
A CHUNK OPERATION FAILED GETNEXT error has occurred on the '%s' file. The chunk operation target record has been deleted.
An OUT OF SYSTEM LOCKS error occurred on the '%s' file. No system locks are currently available. Please attempt the transaction again later.
An INVALID MEMORY SIZE PARAMETER error occurred on the '%s' file. Make certain the value for the Cache Allocation configuration option is large enough to accommodate the required cache size.
A PRE-IMAGE/LOCK DRIVE PARAMTER INVALID error has occurred on the '%s' file. A valid drive letter must be specified for the Pre-Image/Lock File Drive configuration option.
A FILE PARAMETER OUT OF RANGE error has occurred on the '%s' file. The Open Files parameter must be set between 1 and 250, inclusive.
An INITIALIZATION PARAMETER INVALID error occurred on the '%s' file. The configuration options specified contain invalid or unidentifiable values.
A TRANSACTION FILENAME INVALID error has occurred on the '%s' file. The filename specified for the Transaction Filename option is not valid. Check to see that the Transaction Filename option is correct.
A TRANSACTION FILE ACCESS ERROR occurred on the '%s' file. Btrieve is unable to create, open, read, or write to the Transaction file.
A COMPRESSION BUFFER OUT OF RANGE error occurred on the '%s' file. The Compression Buffer Size configuration option must be between 1 and 64 inclusive.
A TASK LIST FULL error occurred on the '%s' file. The Task Entry Table is full. Increasing the Tasks option may remedy.
A STOP WARNING error has occurred on the '%s' file. Btrieve has issued a BTRVSTOP function while files are still open, or a transaction is still active.
A BTRIEVE CANCELLED CURRENT OPERATION error occurred on the '%s' file. The Application has requested to terminate the current Btrieve operation.
A MEMORY ALLOCATION error occurred on the '%s' file. The Btrieve requester cannot allocate sufficient memory for the parameters specified in the BREQPARMS environment variable.
A INVALID OPTION error occurred on the '%s' file. In an OS/2 environment, one or more of the options specified for BREQPARMS is invalid or out of range.
A LOCAL ACCESS DENIED error has occurred on the '%s' file. An attempt was made by the Btrieve requester to access a local data file. The version of WBTRCALL being used does not allow access to local files.
A SPX NOT INSTALLED error has occurred on the '%s' file. NetWare SPX v1.3 or later must be installed on this workstation.
An INCORRECT VERSION OF SPX error has occurred on the '%s' file. The version of SPX installed on this workstation must be v1.3 or later.
A NO AVAILABLE SPX CONNECTION error occurred on the '%s' file. SPX has already established the maximum number of connections it can handle. Please refer to your NetWare documentation for information on increasing SPX connections.
A POINTER PARAMETER INVALID error has occurred on the '%s' file. One of the pointers passed to Btrieve is invalid.
An INVALID ATTRIBUTE error occurred on the '%s' file. Maximizer tried to specify either the segmented or duplicate attribute for an autoincrement key type.
A CHUNK OPERATION on PREVIOUS VERSION error occurred on the '%s' file. Btrieve attempted to perform a chunk operation on a Btrieve file in pre 6.x format. Pre 6.x files do not support chunk operations.
A TRANSACTION TOO COMPLEX error has occurred on the '%s' file. The specified operation has attempted to utilize more than the maximum number of pages in a pre-image file. Break the transaction into two or more smaller transactions.
A PROGRAMMING ERROR occurred on the '%s' file. The error cannot be specifically detected by the Btrieve Record Manager.
A VARIABLE TAIL ALLOCATION error occurred on the '%s' file. The application failed to specify that the file was to use variable length records.
A LOCK PARAMETER OUT OF RANGE error has occurred on the '%s' file. The value specified for the Number of Locks is not valid.
GetListIndex was called with the element "%s", but that element was not found in the currently selected list.
AlignChangedList was called with the element "%s", but that element was not found in the currently selected list.
AlignListDisplay was called with the element "%s", but that element was not found in the currently selected list.
An INVALID POINTER PASSED error has occurred on the '%s' file. The pointer parameter passed into Btrieve is invalid.
A BTRIEVE ALREADY INITIALIZED error occurred on the '%s' file. The Btrieve Record Manager is already initialized.
An UNABLE TO FIND WBTRVRES.DLL error has occurred on the '%s' file. Btrieve is not able to locate the WBTRVRES.DLL resource file.
A BTRIEVE CALLBACK ERROR occurred on the '%s' file. The application attempted to call Btrieve from a Btrieve callback function.
The data file format was not the correct type. Possible causes: it is not a valid Maximizer system data file, or was created with an earlier version of Maximizer Personal.
The data file format was not the correct type. Possible causes: it is not a valid Maximizer system data file, or was created with an earlier version of Maximizer.
The data file format was not the correct type. Possible causes: a read error occurred while reading the data file.
An attempt to find the directory '%s' failed. Possible cause: the specified directory does not exist.
Unable to recognize date, or day exceeds number of days in month.
Value must be between %d and %d inclusive.
An attempt to allocate additional memory to add element "%s" to the current list was unsuccessful.
Invalid or unknown time format.
%s returned an error code of %d.
Specified Directory Does Not Exist.
Value must be between %ld and %ld inclusive
Value must be between %u and %u inclusive.
Value must be between %s and %s inclusive.
An attempt to open the file '%s' failed. Possible cause: the specified file could not be found.
An attempt to open the file '%s' failed. Possible cause: the specified directory could not be found.
An attempt to open the file '%s' failed. Possible cause: there are too many open files.
An attempt to open the file '%s' failed. Possible causes are: opening a read only file for writing, opening a directory instead of a file, the file is locked by another user or, if you are on a network, you do not have sufficient rights.
An attempt to open the file '%s' failed. Possible cause: the specified access code is invalid.
An attempt to read from the file '%s' failed during a read request for %u bytes. Possible causes are: the file is locked by another user or, if you are on a network, you do not have sufficient rights.
An attempt to read from the file '%s' failed during a read request for %u bytes. Possible causes are: the specified file handle was invalid, or does not refer to an open file.
An attempt to write to the file '%s' failed during a write request for %u bytes. Possible causes are: the file is read only or, if you are on a network, you do not have sufficient rights.
An attempt to write to the file "%s" failed during a write request for %u bytes. Possible causes are: the specified file handle was invalid, or does not refer to an open file, or an attempt was made to write to a file that has read-only access.
The combined width of the program header and the version number is greater than 34. This means that the header will be overwritten by the date and time for certain days in certain months (ie. Wednesdays in September). Please shorten the header message.
An INVALID OPERATION error occurred on the '%s' file.
An I/O error occurred on the '%s' file. The file is probably damaged. Refer to your documentation for details on recovering damaged files.
A NO OPEN error occurred on the '%s' file.
A KEY NOT FOUND error has occurred on the '%s' file. Refer to your documentation for details on recovering damaged files.
A DUPLICATES error has occurred on the '%s' file.
An INVALID KEY NUMBER error occurred on the '%s' file.
A DIFFERENT KEY NUMBERS error occurred on the '%s' file.
An INVALID POSITIONING error occurred on the '%s' file. Refer to your documentation for details on recovering damaged files.
An unidentified error has occurred on the '%s' file.
The selected record could not be found. The record was probably deleted by another user.
Press ESCAPE to cancel
Please Wait
or
This version of Maximizer allows a maximum of 101 Client and Address records. To insert more, please upgrade your copy of Maximizer. See Help - About Maximizer 3.0is for ordering instructions.
File name is missing or matches one of the files Maximizer uses.
The selected record has been marked private by another user.
A COMPRESSION BUFFER TOO SHORT error has occured on the '%s' file. The record is longer than the value specified for the compression buffer.
A FILE ALREADY EXISTS error has occured on the '%s' file. An attempt has been made to create a file that already exists.
A PERMISSION error has occured on the '%s' file. The requested operation cannot be performed due to an operating system restriction. Possibly the user does not have sufficient rights to open or create the file; or, another user has this file open.
The redirection table or the server routing table is full. This error can occur if you attach to additional servers or map to more drives after you have loaded BREQUEST. Reload BREQUEST, specifying a larger number for the /R or /S option.
BREQUEST cannot establish a session with the server. Either BREQUEST has not been started for the device controlling the '%s' file, or the server is not active. Verify that BSERVER is active on the server to which the device has been redirected.
The number of transactions you specified when you loaded BSERVER has been exceeded. Specify a larger number for the transactions parameter for BSERVER.
A previously established session is no longer valid due to an error at the workstation or the file server, or on the network. Verify that the file server is still attached and then reload BREQUEST at the workstation.
The SPX connection table is full. Reload SPX specifying a higher value for the connection table. Refer to the Netware Supervisor Reference manual for more information.
A DATA MESSAGE TOO SMALL error has occurred on the '%s' file. The record length of the file is either longer then the record length parameter of BSERVER or the data message option of BREQUEST. Determine the proper length and reload the appropriate program
An END OF FILE error occurred on the '%s' file.
A MODIFIABLE error occurred on the '%s' file.
An INVALID FILE NAME error occurred on the '%s' file.
A FILE NOT FOUND error occurred on the '%s' file. Either the file does not exist or you do not have proper access rights to it.
An EXTENSION error occurred on the '%s' file. Btrieve cannot find the extension file for a partitioned file.
A PRE-OPEN error occurred on the '%s' file. The disk may be full, the pre-image file is missing or damaged. Refer to your documentation for details on recovering damaged files.
A PRE-IMAGE I/O error occurred on the '%s' file. Either the disk is full or the pre-image file is damaged. Refer to your documentation for details on recovering damaged files.
An EXPANSION error occurred on the '%s' file. The directory structure could not be flushed for the expanded file partition. Check for a damaged disk.
A CLOSE error occurred on the '%s' file. The directory structure could not be flushed for the file. Check for a damaged disk.
A DISK FULL error occurred on the '%s' file. The disk is full and will not allow expansion of the file.
An UNRECOVERABLE error occurred on the '%s' file. File integrity cannot be guaranteed. Refer to your documentation for details on recovering damaged files.
A RECORD MANAGER INACTIVE error occurred on the '%s' file. The BTRIEVE program must be loaded prior to loading this program.
A KEY BUFFER error occurred on the '%s' file.
A RECORD BUFFER error occurred on the '%s' file. The retrieved record is longer than the buffer. The record is truncated.
A POSITION BLOCK error occurred on the '%s' file. The position block parameter is not 128 bytes long.
A PAGE SIZE error occurred on the '%s' file.
A CREATE I/O error occurred on the '%s' file. The file could not be created. Possible causes are a full disk directory, a full disk, the disk is write protected, the user does not have rights to the directory and/or file, or the file is already in use.
A NUMBER OF KEYS error occurred on the '%s' file.
A KEY POSITION error occurred on the '%s' file.
A RECORD LENGTH error occurred on the '%s' file.
A KEY LENGTH error occurred on the '%s' file.
A FILE NAME error occurred on the '%s' file. The file is either not a Btrieve file or was created by an earlier version of Btrieve.
An EXTEND error occurred on the '%s' file. The file has already been extended and may not be extended again.
An EXTEND I/O error occurred on the '%s' file. The file cannot be extended. Possible causes are that the disk directory is full, the disk is full, or the disk is write protected.
An EXTEND NAME error occurred on the '%s' file. The file name specified for the extended partition is not valid.
A DIRECTORY error occurred on the '%s' file. An error occurred switching between the current directory and the directory containing the file. Either the current directory or the file directory is invalid.
A TRANSACTION error occurred on the '%s' file. The transaction operation cannot be performed because the /T option was not specified when the record manager was loaded.
A BEGIN TRANSACTION error occurred on the '%s' file. A begin transaction was issued while another transaction was active. Transactions cannot be nested.
A TRANSACTION CONTROL FILE error occurred on the '%s' file. Possible causes are that the disk is full, the disk is write-protected, or the transaction control file has been deleted.
An END/ABORT error occurred on the '%s' file. An end or abort transaction operation was issued without a corresponding begin transaction operation.
A TRANSACTION MAX FILES error occurred on the '%s' file. An attempt was made to update more than the maximum number of files allowed within a transaction. The maximum is 12.
A TRANSACTION OPEN/CLOSE error occurred on the '%s' file. An attempt was made to open or close a file while a transaction was active. These are prohibited because they may change the pre-image file.
An INCOMPLETE ACCELERATED ACCESS error occurred on the '%s' file. The file was previously opened in accelerated mode and not successfully closed. The file's integrity cannot be ensured.
An INVALID DATA RECORD ADDRESS error occurred on the '%s' file. Either the address is outside the file's bounds or it is not on a record boundary within a data page. Refer to your documentation for details on recovering damaged files.
A NULL KEY PATH error occurred on the '%s' file. An attempt has been made to use get direct to establish an access path for a key whose value is null in the corresponding record.
An INCONSISTENT KEY FLAGS error occurred on the '%s' file. If a key has multiple segments, the duplicate, modifiable, and null attributes should be the same for each segment in the key.
An ACCESS DENIED error occurred on the '%s' file. Either you are trying to update a read-only file or a file that requires a password for updates and no password was specified on the file open.
A MAXIMUM OPEN FILES error occurred on the '%s' file. The maximum number of files opened in accelerated mode has been reached. Restart the record manager with a larger /M option or a smaller /P option to allocate more buffers.
An INVALID ALTERNATE SEQUENCE error occurred on the '%s' file. The first byte in an alternate collating sequence does not contain the hexadecimal value AC or the supplemental index specified an alternate collating and none exists for the file.
A KEY TYPE error occurred on the '%s' file. An attempt has been made to define an alternate collating sequence for a binary key or key segment or to create a file or a supplemental index with an invalid extended key type.
An OWNER ALREADY SET error occurred on the '%s' file. An attempt was made to set the owner name of a file that already has an owner name.
An INVALID OWNER error occurred on the '%s' file.
A CACHE WRITE error occurred on the '%s' file. The system reported an I/O error while trying to make a cache buffer available.
An INVALID INTERFACE error occurred on the '%s' file. A version of the record manager prior to 4.10 was loaded.
A VARIABLE PAGE UNREADABLE error occurred on the '%s' file. This error usually indicates file damage to one or more pages in the file.
A CONFLICT error occurred on the '%s' file. The update/delete operation cannot be performed because the record has been changed by another station since this station read it.
A LOCK error occurred on the '%s' file. The lock or unlock function call to the O/S failed, the lock table is full or the record was never locked. Try reloading the record manager with a larger value for the /L option.
A LOST POSITION error occurred on the '%s' file. Refer to your documentation for details on recovering damaged files.
A READ OUTSIDE TRANSACTION error occurred on the '%s' file.
A RECORD IN USE error occurred on the '%s' file. An attempt has been made to lock a record that is currently locked by another handle or to access a file within a transaction while another station held active record locks in that file.
A FILE IN USE error occurred on the '%s' file. An attempt was made to open a file, lock a record, or access a record within a transaction while another handle holds the transaction lock on the file.
A FILE TABLE FULL error occurred on the '%s' file. Specify a larger /F option when loading the record manager.
A HANDLE FULL error occurred on the '%s' file. The handle table is full. Increase the files parameter in the CONFIG.SYS file.
A MODE error occurred on the '%s' file. An attempt was made to open a file with an incompatible mode.
A DEMO error occurred on the '%s' file. An attempt has been made to add more than 24 records to a file using the demonstration version of Btrieve.
An INCOMPLETE INDEX error occurred on the '%s' file. A supplemental index is damaged.
An EXPANDED MEMORY error occurred on the '%s' file. This error can indicate an incompatiblity with another application which uses expanded memory.
An INCOMPATIBLE LOCK TYPES error occurred on the '%s' file. The application attempted to mix single record locks and multiple record locks.
Insufficient memory to complete list build. List truncated at %d entries. Make more memory available.
Number exceeds 9,999,999.99.
WARNING! A dates delete performed from this name list will PERMANENTLY delete ALL marked specified date information associated with the MARKED client(s) or contact(s). Number of entries marked: %d.
WARNING! A note delete performed from this name list will PERMANENTLY delete ALL notes associated with the MARKED client(s) or contact(s). Number of entries marked: %d.
Error in line %d of %s. Path '%s' is invalid or does not exist.
Error in line %d of %s. Path '%s' is not a directory.
Insufficient memory to complete list build. Try shutting down other applications if you need to complete this list build.
Deletion of this table could result in the deletion of description information throughout your files.
Deletion of this entry could result in the deletion of description information throughout your files.
Ending date must be greater than or equal to starting date.
Duplicate or missing ID number.
Name is a required field.
Maximizer File Backup. COPYRIGHT Maximizer Technologies Inc. All Rights ReservedBackup File Directory :
WARNING!!! ALL of your current Maximizer data files are about to be DESTROYED and replaced with your backup. Are you sure you wish to continue?
Maximizer File Backup. COPYRIGHT Maximizer Technologies Inc. All Rights Reserved.
Diskette is out of sequence. Insert the correct diskette.
The Backup file '%s' is the wrong version. You may insert the proper disk or abort the operation.
The Backup file '%s' cannot be found. You may insert the correct disk or abort the operation.
A drive not ready error occurred while reading/writing to the file '%s'. Possible causes are: the disk is improperly inserted in the drive, the disk drive door is not closed, or there is no disk in the drive.
A write protection error has occurred while writing to the file '%s'. The diskette in drive is write-protected. NOTE: before you remove write-protection ensure that the disk does not contain important information.
An unknown unit error has occurred while reading/writing to the file '%s'. Possible causes are: a device driver has been passed an invalid sub-unit number. Contact your computer hardware dealer.
A data error occurred reading/writing to the file '%s'. Possible causes are: a defective spot on the disk. If the disk is removable, try another one. If this error has occurred on your hard drive, contact your computer hardware dealer.
A seek error has occurred while reading/writing to the file '%s'. Possible causes are: a track on the disk containing the data could not be located. If this error has occurred on your hard drive, contact your computer hardware dealer.
An unknown media error has occurred while reading/writing to the file '%s'. Possible causes are: a non-DOS disk in drive, or disk has been formatted using a different version of DOS.
A sector not found error has occurred while reading/writing to the file '%s'. Possible causes are: a sector on the disk containing the data could not be located. If this error has occurred on your hard drive, contact your computer hardware dealer.
A printer not ready or out of paper error has occurred. Possible causes are: printer is off, printer is not online, printer cable is not firmly connected, or printer is out of paper.
A write fault error has occurred while writing to the file '%s'. Possible causes are: the disk is improperly inserted in the drive.
A read fault error has occurred while reading from the file '%s'. Possible causes are: the disk is improperly inserted in the drive.
A general failure error has occurred reading/writing to the file '%s'. Possible causes are: an unformatted/improperly formatted disk in drive, or a severely damaged disk. If this error has occurred on your hard disk, contact your computer hardware dealer.
WARNING!!! All of your MARKED Maximizer data files are about to be DESTROYED and replaced with your backup. Are you sure you wish to continue?
WARNING!!! All Maximizer backup files in the target directory '%s' will be ERASED. Are you sure you wish to continue?
WARNING!!! All marked Maximizer backup files in the target directory '%s' are about to be ERASED. Are you sure you wish to continue?
%d%% Complete.
Disk No. %d
WARNING!!! You are about to restore the '%s' file to a DIFFERENT directory (%s) than it was originally backed up from (%s). Are you sure you wish to continue.
The target '%s' file is from a previous version of Maximizer.
An Environment mismatch error has occurred.
A memory allocation error has occurred.
A file access error has occured.
A read/write error has occurred.
A bad input word length (word too long) error has occurred.
(.txt)